Walkthrough

In uploadStream inside src/internal/client.ts, the multipart chunk loop's partNumber is now initialized to 0 and incremented before the oldParts lookup, changing the part-number-to-chunk mapping. A new post-loop guard aborts the multipart upload and falls back to uploadBuffer with an empty object when eTags is empty.

Changes

Multipart Upload Part Numbering and Empty-Parts Fallback

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Poem

🐇 A part number shifted, now starts from zero,
The chunks line up right — this rabbit's a hero!
An empty eTags? Abort and retreat,
Upload a blank buffer, keep the flow neat.
No empty multipart shall pass on my watch,
The stream hops along without a botch! 🌿

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}